This pull request has merge conflicts that must be resolved before it can be merged.

The pointers from py > python are good. IMO whatever github uses we should mirror.

So do we actually have cases for all these types or are they speculative? I.e. ini files don't really have a particular format do they? When is "ignore" used? diff would be great in some cases but is it a standardized format? I can imagine using this to show when you make changes in a file.

As @wbamberg suggests here https://github.com/orgs/mdn/discussions/170#discussioncomment-3352639 we need to make sure that the supported set is documented.

Who can review/merge this nowdays?

The pointers from py > python are good. IMO whatever github uses we should mirror.

I'd be happy to add the alias back in! I removed it because both py and python are interchangeable with Prism, so we don't need to map it ourselves.

So do we actually have cases for all these types or are they speculative?

A few of these are speculative (such as SQL, URI, SCSS and Less). I basically skimmed through the Prism supported list to find web-related and Git-related languages, and added them in.

ini files don't really have a particular format do they?

They do, actually! Though this one's a speculative add, so I'm happy to take it out!

When is "ignore" used?

Ignore includes .gitignore, which we have included sample content for a few times.

diff would be great in some cases but is it a standardized format?

It is a standard format, yes!

The pointers from py > python are good. IMO whatever github uses we should mirror.

I'd be happy to add the alias back in! I removed it because both py and python are interchangeable with Prism, so we don't need to map it ourselves.

If we don't need to map it ourselves then it doesn't need to be added back in. But the docs need to make clear what is supported.

So do we actually have cases for all these types or are they speculative?

A few of these are speculative (such as SQL, URI, SCSS and Less). I basically skimmed through the Prism supported list to find web-related and Git-related languages, and added them in.

The thing that kicked this off was nginx and apache, and I'd been hoping for "pug". My original thinking was add everything, but since Will has spoken against this, we really need to agree the policy before we put this in. I'll comment the set on the issue and lets see if we can get broad agreement.

FYI, prism-react-renderer has its own list of default-included language list, and it seems to be aiming for web-related ones.

@queengooborg So I think we have settled about what languages can be added, and under what conditions: https://github.com/orgs/mdn/discussions/170#discussioncomment-3403112

Do these rules make sense for you?

If so,

• the alias list will need to contain just one identifier for the languages that we support (even if Prism supports them natively),
• web idl needs to be removed or even better COMMENTED out with a note "block list"
• are you willing to add these to the docs?

@queengooborg Ready for me to merge?

Yep, go for it! If we want to add or remove any syntax languages, we can do so down the line. 👍

Thanks very much!!!!

That's awesome, so which one of you is updating https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN#example_code_blocks in line with https://github.com/orgs/mdn/discussions/170#discussioncomment-3403112 ?

I already added pug and yaml in mdn/content#19806, and wasm was already in the list.